Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

staging-next 2024-08-06 #332764

Merged
merged 578 commits into from
Aug 14, 2024
Merged

staging-next 2024-08-06 #332764

merged 578 commits into from
Aug 14, 2024

Conversation

mweinelt and others added 30 commits August 6, 2024 18:18
The hook relied on the `test` command passed to `setup.py`, which has
long been deprecated and finally removed in setuptools 72.0.
The source is also reused in pytest-server-fixtures, pytest-shutil and
pytest-virtualenv, which now inherit the patch.
These tests have forced the hydra job for electrum-ltc to run into a
timeout.
Accessing packaging via setuptools.extern is dead.
Depending on aiohttp yields an infinite recursion.
Requests in 2.32.3 caused a regression in the code path that loads the
default certificate authorities, breaking downstream consumers like
httpie in the process.

The patch series fixing this is currently still a draft, since tests are
missing, but it at least fixes the reproducer and httpie.
mweinelt and others added 5 commits August 13, 2024 02:36
home-assistant: support imgw_pib component
add python to nativeBuildInputs to fix build
This reverts commit 0df677d.

This was reverted on master, but the the fixes had already landed on
staging-next, so it shouldn't have been revert here.
[staging-next] qt6.qtdeclarative: slightly less bad hack to make it build on Darwin again
@ofborg ofborg bot added the 2.status: merge conflict This PR has merge conflicts with the target branch label Aug 13, 2024
@ofborg ofborg bot removed the 2.status: merge conflict This PR has merge conflicts with the target branch label Aug 13, 2024
@mweinelt mweinelt merged commit 9ccfa87 into master Aug 14, 2024
14 checks passed
@spiage spiage mentioned this pull request Aug 14, 2024
@mhorbul
Copy link

mhorbul commented Aug 15, 2024

After this merge awscli2-2.17.18 build started to fail

building '/nix/store/a36sqbcyv57lgkv6kw1494n8zm95x1i0-awscli2-2.17.18.drv'...
error: builder for '/nix/store/a36sqbcyv57lgkv6kw1494n8zm95x1i0-awscli2-2.17.18.drv' failed with exit code 1;
       last 10 log lines:
       > tests/unit/customizations/logs/test_startlivetail.py::LiveTailKeyBindingsTest::test_t_key_binding
       >   /nix/store/kcm5282kss1mnil624lccr7y8wqg75vk-python3-3.11.9/lib/python3.11/enum.py:714: RuntimeWarning: coroutine 'AsyncMockMixin._execute_mock_call' was never awaited
       >     return cls.__new__(cls, value)
       >   Enable tracemalloc to get traceback where the object was allocated.
       >   See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > FAILED tests/unit/customizations/cloudtrail/test_validation.py::TestSha256RSADigestValidator::test_validates_digests - ValueError: key_size must be at least 1024-bits.
       > ======= 1 failed, 4097 passed, 1 skipped, 2 warnings in 81.00s (0:01:20) =======
       For full logs, run 'nix log /nix/store/a36sqbcyv57lgkv6kw1494n8zm95x1i0-awscli2-2.17.18.drv'.

@K900
Copy link
Contributor

K900 commented Aug 15, 2024

This is normal for staging cycles. Not every regression can be addressed in a reasonable time.

@kirillrdy
Copy link
Member

awscli2 fixed #334858

@maralorn
Copy link
Member

maralorn commented Aug 21, 2024

It seems like the periodic merges master -> staging-next, staging-next -> staging. Are somehow happening in my name. See e.g. here: https://github.com/NixOS/nixpkgs/actions/runs/10489420359

I currently get one alert every 6h because staging-next -> staging gives a merge conflict.

I think this has been going on for ages, but I recently changed the way I engage with GitHub notifications and now this alerts are a bit annoying to me.

According to this help article https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/notifications-for-workflow-runs
I assume this is happening because I renamed the workflow and therefor apparently count as it’s creator, even though there have been a lot of later changes to the workflow, but none of those changed the schedule or the name.

If anyone is interested in receiving these alerts, then according to the above help article they need to disable and reenable the workflow in the GitHub ui, making them the "actor" of the workflow.

Otherwise I am trying to figure out how to silence them for me, but I am not completely optimistic that I can.

@maralorn
Copy link
Member

Yeah, as far as I can tell, I can just disable workflow notifications globally for all of GitHub which would not make my employer happy.

So if anyone would be willing to take this from me, because they either deal with staging more than I do or because they don’t care much about GitHub notifications anyway, I would be very thankful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 6.topic: emacs Text editor 6.topic: haskell 6.topic: kernel The Linux kernel 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 6.topic: nodejs 6.topic: php 6.topic: python 6.topic: qt/kde 6.topic: ruby 6.topic: rust 6.topic: stdenv Standard environment 6.topic: systemd 6.topic: zig 8.has: changelog 8.has: clean-up 8.has: documentation This PR adds or changes documentation 8.has: module (update) This PR changes an existing module in `nixos/` 8.has: package (new) This PR adds a new package 10.rebuild-darwin: 501+ 10.rebuild-darwin: 5001+ 10.rebuild-darwin-stdenv This PR causes stdenv to rebuild 10.rebuild-linux: 501+ 10.rebuild-linux: 5001+ 10.rebuild-linux-stdenv This PR causes stdenv to rebuild
Projects
None yet
Development

Successfully merging this pull request may close these issues.